<?xml version="1.0" standalone="yes"?>
<?xml-stylesheet type="text/xsl" href="..\..\XSLTemplates\ErrorsStyleSheet.xsl"?>
<Error>
<ErrorNumber>15370</ErrorNumber>
<ErrorFamily>Autoloader</ErrorFamily>
<ErrorMessage>
ALE: Timeout moving the cr from drum to home
Timeout moving the cr from vr to home
Timeout moving the cr, it is lost!!!
Timeout moving the cr from home to vr
Timeout moving the cr from home to drum
Timeout moving the VR to Neutral
Timeout moving the VR to Drum
Timeout moving the VR to Tray
Timeout moving the tape roller up
Timeout moving the tape roller down
</ErrorMessage>
<AppliesTo>
<UnnumberedList>
<ListItem><Text>Trendsetter_400/800_Proofing</Text></ListItem>
</UnnumberedList>
</AppliesTo>
<OperatorAction>
<DescriptionText><text>
Select the RESUME button from the workstation dialog box.  If that does not
correct the problem, select MEDIA CLEARED from the workstation dialog box and manually
remove the media (donor and receiver). If the problem persists, call Creo service.
</text></DescriptionText>
</OperatorAction>
<ServiceInformation>
<DescriptionText><text>
Determine if the actuator is moving properly over it's full range of
motion.  You can move all actuators manually, or from the diagnostic
monitor using the "vr" or "cr" commands.  If the actuator  is not moving
quickly and smoothly over it's entire range of motion, check for mechanical
faults, air-flow problems, and obstructions.  If the actuator moves well
over it's range of motion, check the sensors with the "proof" command
and verify that they are operating correctly.  If the sensors aren't, then
the problem is likely faulty wiring or faulty sensor alignment.  Note
that the VR does not operate properly unless the proof loader is locked
into it's upright position (position=1), so don't try and test it with
the proof loader open.
</text></DescriptionText>
</ServiceInformation>
<ServiceInformation>
<DescriptionText><text>
The sensors can be over-ridden using the "alproof si" parameter.  This
will allow the machine to operate, but in a much slower and more
dangerous manner. In this state, the machine should only be used
if absolutely necessary and if it will be fixed very soon.  When the
sensors are disabled, the machine is running "blind", so it could incur
additional damage if used.  Use extreme caution.
</text></DescriptionText>
</ServiceInformation>
<Cause>
An actuator has timed-out while moving.  This is caused by a mechanical
or eletrical fault, or an obstruction preventing the actuator from moving
freely.  It is also possible that the sensors are working and the actuator
is moving over its full range, but is taking too long to move.  In this
case, the mechanical problem causing the slow motion must be fixed.
</Cause>
<SeeAlso>
<UnnumberedList>
<Link><LinkAddress>../commands/act.xml</LinkAddress><LinkTitle>Command: act</LinkTitle></Link>
<Link><LinkAddress>../commands/vr.xml</LinkAddress><LinkTitle>Command: vr</LinkTitle></Link>
<Link><LinkAddress>../commands/tr.xml</LinkAddress><LinkTitle>Command: tr</LinkTitle></Link>
<Link><LinkAddress>../commands/cr.xml</LinkAddress><LinkTitle>Command: cr</LinkTitle></Link>
<Link><LinkAddress>../commands/proof.xml</LinkAddress><LinkTitle>Command: proof</LinkTitle></Link>
<Link><LinkAddress>../nvs/alproof_cfg_si.xml</LinkAddress><LinkTitle>NVS: alproof si</LinkTitle></Link>
</UnnumberedList>
</SeeAlso>
<OtherLinks>
<Link><LinkAddress>..\..\ShowAllErrors.htm</LinkAddress><LinkTitle>Firmware 0 Error Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllCommands.htm</LinkAddress><LinkTitle>Firmware 0 Command Index</LinkTitle></Link>
<Link><LinkAddress>..\..\ShowAllNVS.htm</LinkAddress><LinkTitle>Firmware 0 NVS Index</LinkTitle></Link>
</OtherLinks>
<Updated>
Updated: Wed Jul 16 19:33:05 2008 PST
</Updated>
<Links>
</Links>
</Error>
